Management device for serving network or device and resource management method thereof

ABSTRACT

Disclosed is a method of managing resources to allow networks or devices coexist. To this end, a neighbor discovering method of an apparatus including a coexistence manager (CM) includes: receiving, by the CM, a request from a television band device (TVBD) network or device served by the CM; obtaining, by the CM, neighbor information of the TVBD network or device in response to the request; and transmitting, by the CM, the obtained neighbor information to the TVBD network or device, wherein the neighbor information includes an identifier of a neighbor TVBD network or device interfering the TVBD network or device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is the National Stage filing under 35 U.S.C. 371 of International Application No. PCT/KR2011/009663, filed on Dec. 15, 2011, which claims the benefit of U.S. Provisional Application Ser. No. 61/432,203, filed on Jan. 13, 2011, U.S. Provisional Application Ser. No. 61/468,063, filed on Mar. 27, 2011, U.S. Provisional Application Ser. No. 61/469,068, filed on Mar. 29, 2011 and U.S. Provisional Application Ser. No. 61/469,061, filed on Mar. 29, 2011, the contents of which are all incorporated by reference herein in their entirety.

TECHNICAL FIELD

The present invention relates to a management device for serving a network or a device and a resource management method thereof.

BACKGROUND ART

Conventionally, allotment of frequency for a new service or allotment of frequency to new service providers was led by the government.

In particular, when new comers have entered, the government allotted a new frequency to them through an auction, or the like, or collects an existing frequency from an existing service provider and re-deploy it for a different service provide, thereby allotting frequency as limited resource.

However, recently, as demand for wireless data traffic is explosively increased in the wake of the spreading of various wireless Internet-based applications such as open terminal platform, App store, mobile VoIP, and the like, the government-driven frequency allotment is considered very ineffective and it is increasingly difficult to secure a new frequency on a table of frequency allocation fundamentally.

In particular, in line with the rapid growth of broadcast and communication systems, next-generation communication systems have been designed in a converged form of several networks and increasingly complicated, and the necessity of interaction or interworking is extending. Also, development of communication technologies and services has increased the frequency of use in frequency resources and the occupancy of a particular frequency band in a fixed manner to provide excellent communication techniques and services has caused severe depletion of frequency

Recently, a frequency sharing scheme has come to prominence as a solution to the problems. This starts from a point of view that the current frequency shortage phenomenon is resulted from an existing partition type frequency management scheme and, although frequency appears to be insufficient on the table of frequency allocation but such frequency shortage can be solved through a sharing scheme.

As the depletion of frequency resources has been admitted to be significant worldwide, FCC (Federal Communications Commission) to the US decided to apply a cognitive radio technology, a frequency sharing technology, to a TV white space and revised a relevant regulation.

Such a movement is gradually extending, and in 2009, England has permitted the use of a CR (Cognitive Radio)-based frequency sharing technology in a band, included in a TV broadcast band, which is not spatially used, namely, a white space band. EU is discussing the introduction of the CR-based frequency sharing technology, and, also domestically, preparations for a frequency sharing policy using the white space band are being made.

The CR technology refers to a system in which a communication device observes a communication environment by itself, determines and selects an operation scheme for optimum communication, and makes a plan for a future determination process from a previous communication experience. Namely, the CR technology locates idle resource (spectrum hole, white space) which has low utilization or is temporally/spatially not used among frequency bands allocated to unlicensed band, and adaptively and opportunistically uses it. In this case, when a primary user having a license for a corresponding band is discovered, the use of the corresponding band should be stopped or transmit power is adjusted not to cause damage to the primary user.

DISCLOSURE Technical Problem

Embodiments proposed in the present disclosure aim at solving the foregoing problems. In other words, in an embodiment of the present invention, networks or devices substantially in an interference relationship (i.e., which substantially interfere with each other) are discovered, and resources are managed to allow networks or devices to effectively coexist in consideration of the substantial interference relationship.

Technical Solution

An aspect of the present invention provides a method for managing resource to allow TV band networks or devices to coexist.

According to an aspect of the present invention, there is provided a neighbor discovering method of an apparatus including a coexistence manager (CM), including: receiving, by the CM, a request from a television band device (TVBD) network or device served by the CM; obtaining, by the CM, neighbor information of the TVBD network or device in response to the request; and transmitting, by the CM, the obtained neighbor information to the TVBD network or device, wherein the neighbor information includes an identifier of a neighbor TVBD network or device interfering the TVBD network or device.

According to another aspect of the present invention, there is provided an apparatus including a coexistence manager (CM), including: a transceiver unit configured to receive a request from a television band device (TVBD) network or device served by the CM; and a controller configured to obtain neighbor information of the TVBD network or device in response to the request, wherein the transceiver unit transmits the obtained neighbor information to the TVBD network or device, and the neighbor information includes an identifier of a neighbor TVBD network or device interfering the TVBD network or device.

Advantageous Effects

According to an embodiment disclosed in the present disclosure, a management device effectively allocates resources between networks or devices on the basis of a substantial interference relationship, thereby maximizing utilization of limited resources.

DESCRIPTION OF DRAWINGS

FIG. 1 is a schematic block diagram of a coexistence system according to an embodiment of the present disclosure.

FIG. 2 is a schematic block diagram of a coexistence system according to another embodiment of the present disclosure.

FIG. 3 is a view showing an example of a disposition of the coexistence system according to an embodiment of the present disclosure.

FIG. 4 shows an operation of the coexistence system according to an embodiment of the present disclosure.

FIG. 5 is a view showing another example of a disposition of the coexistence system according to an embodiment of the present disclosure.

FIGS. 6A and 6B are views showing an operation of a CDIS/CDB 400.

FIG. 7 is a view showing coexistence contours.

FIG. 8 is a view showing an example of a coexistence whitespace map (CWM) or a coexistence map in the environment of FIG. 7.

FIG. 9 is a flow chart illustrating a process of searching for a neighbor according to an embodiment of the present disclosure.

FIG. 10 is a view showing information regarding available channels of a television band device (TVBD) network or device according to an embodiment of the present disclosure.

FIG. 11 is a conceptual view showing a process for searching for a neighbor according to a first embodiment of the present disclosure.

FIG. 12 is a conceptual view showing a process for searching for a neighbor according to a second embodiment of the present disclosure.

FIG. 13 is a flow chart illustrating a process of allocating resources by a coexistence manger (CM) according to embodiments of the present disclosure.

FIG. 14 is a flow chart illustrating a process of updating a neighbor list according to embodiments of the present disclosure.

FIG. 15 is a flow chart illustrating a process for receiving occupied channel information and interference level information from the TVBD network or device by the CM according to an embodiment of the present disclosure.

FIG. 16 is a flow chart illustrating a process for receiving occupied channel information and interference level information from the TVBD network or device by the CM according to another embodiment of the present disclosure.

FIG. 17 is a flow chart illustrating a process of discovering a neighbor set of the TVBD network or device 100 by the CM 300 according to an embodiment of the present disclosure.

FIG. 18 is a flow chart illustrating a process of switching a service by the TVBD network of device 100 or the CM 300 according to an embodiment of the present disclosure.

FIG. 19 is a flow chart illustrating a process of switching a service by the TVBD network of device 100 or the CM 300 according to another embodiment of the present disclosure.

FIG. 20 is a flow chart illustrating a process of selecting a service by the TVBD network of device 100 according to another embodiment of the present disclosure.

FIG. 21A is a view showing semantics of a service primitive of a coexistence service changing request according to an embodiment of the present disclosure.

FIG. 21B is a view showing semantics of a service primitive of a coexistence service change notification according to an embodiment of the present disclosure.

FIG. 21C is a view showing semantics of a service primitive of a coexistence service changing response according to an embodiment of the present disclosure.

FIG. 21D is a view showing semantics of a service primitive of a coexistence service change confirmation according to an embodiment of the present disclosure.

FIG. 22 is a flow chart illustrating a process of switching a service by the CM 300 according to embodiments of the present invention.

FIG. 23 is a schematic block diagram of the CM 300 according to the present disclosure.

BEST MODES

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. Unless otherwise defined, all terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains, and should not be interpreted as having an excessively comprehensive meaning nor as having an excessively contracted meaning. If technical terms used herein is erroneous that fails to accurately express the technical idea of the present invention, it should be replaced with technical terms that allow the person in the art to properly understand. The general terms used herein should be interpreted according to the definitions in the dictionary or in the context and should not be interpreted as an excessively contracted meaning.

In the present application, it is to be understood that the terms such as “including” or “having,” etc., are intended to indicate the existence of the features, numbers, operations, actions, components, parts, or combinations thereof disclosed in the specification, and are not intended to preclude the possibility that one or more other features, numbers, operations, actions, components, parts, or combinations thereof may exist or may be added.

While terms such as “first” and “second,” etc., may be used to describe various components, such components must not be understood as being limited to the above terms. The above terms are used only to distinguish one component from another. For example, a first component may be referred to as a second component without departing from the scope of rights of the present invention, and likewise a second component may be referred to as a first component. The term “and/or” encompasses both combinations of the plurality of related items disclosed and any item from among the plurality of related items disclosed.

When a component is mentioned as being “connected” to or “accessing” another component, this may mean that it is directly connected to or accessing the other component, but it is to be understood that another component may exist therebetween. On the other hand, when a component is mentioned as being “directly connected” to or “directly accessing” another component, it is to be understood that there are no other components in-between.

The exemplary embodiments of the present invention will now be described with reference to the accompanying drawings, in which like numbers refer to like elements throughout. In describing the present invention, if a detailed explanation for a related known function or construction is considered to unnecessarily divert the gist of the present invention, such explanation has been omitted but would be understood by those skilled in the art. The accompanying drawings of the present invention aim to facilitate understanding of the present invention and should not be construed as limited to the accompanying drawings. The technical idea of the present invention should be interpreted to embrace all such alterations, modifications, and variations in addition to the accompanying drawings.

Hereinafter, a term of terminal is used, and the terminal may be called by other names such as UE (User Equipment), ME (Mobile Equipment), MS (Mobile Station), UT (User Terminal), SS (Subscriber Station), MSS (Mobile Subscriber Station), wireless device, handheld device, or AT (Access Terminal).

IEEE 802.11 wireless local area network (WLAN) standard provides a transfer rate of 54 Mbps (IEEE 802.11a) using an unlicensed band at 2.4 GHz or 5 GHz.

IEEE 802.11g provides a transfer rate of 54 Mbps by applying an orthogonal frequency-division multiplexing (OFDM) at 2.4 GHz.

IEEE 802.11n provides a transfer rate of 300 Mbps with respect to four spatial streams by applying MIMO-OFDM. IEEE 802.11n supports a channel bandwidth of up to 40 MHz, and in this case, it provides a transfer rate of 600 Mbps.

TV whitespace (TVWS) includes VHF bands (54˜60, 76˜88, 174˜216 MHz) and a UHF band (470˜698 MHz) allocated to a broadcast TV system. The TV whitespace refers to a licensed frequency band permitted to be used by an unlicensed device under the conditions that the unlicensed device does not hamper communication of a licensed device (a TV, a wireless microphone, or the like) operating at a corresponding frequency band.

Meanwhile, TVWS, an acronym of TV white space, refers to an empty frequency band not used by a broadcast provider at a VHF and UHF frequency band distributed for a TV broadcast, and also refers to an unlicensed band any one may use when conditions for a propagation regulation are met. Namely, the TV white space may refer to frequency information for broadcasting. In detail, spatially, TV white space refers to a band empted to avoid frequency interference between broadcast providers, a frequency band not used by area, or an area broadcasting propagation does not reach, and temporally, TV white space refers to an empty broadcast frequency in a time duration in which a broadcast provider does not transmit a broadcast at dawn. Broadcast reception by a TV viewer as a client of a broadcast provider should not be interfered with, and a wireless microphone device performing communication by a small output by using a portion of the band (TVWS) should not also be influenced.

At bands of 512˜608 MHz and 614˜698 MHz, every unlicensed devices, except for some particular cases, are permitted to operate, but bands of 54˜60 MHz, 76˜88 MHz, 174˜216 MHz, and 470˜512 MHz are permitted only for communication between fixed devices. A fixed device refers to a device that performs transmission only at a determined position.

An IEEE 802.11 TVWS terminal is an unlicensed device operating by using IEEE 802.11 MAC and PHY in a TV white space spectrum.

An unlicensed user who wants to use TV whitespace should provide a protection function with respect to a licensed user. Thus, before starting transmission in a TV band, whether or not a licensed user is occupying a corresponding band must be checked or ascertained

To this end, the unlicensed device is connected to a geo-location database through the Internet or a dedicated network to obtain information regarding a list of channels which are available in a corresponding area. The geo-location database refers to a database storing and managing licensed devices registered thereto, location information of the licensed devices, and information regarding channels which are dynamically changed as devices use them over channel occupied time.

A station (STA) performs a spectrum sensing mechanism. Here, as the spectrum sensing mechanism, an energy detection scheme, a feature detection scheme, or the like, is utilized. When the strength of a reception signal is equal to or greater than a certain value or when a DTV preamble is detected, the station (STA) determines that an incumbent user is using a particular channel. When the station (STA) determines that an incumbent user is using a channel contiguous to a channel currently used by the STA or an access point (AP) connected to the STA, the STA and the AP should lower transmission power.

FIG. 1 is a schematic block diagram of a coexistence system according to an embodiment of the present disclosure. As shown in FIG. 1, a coexistence system according to an embodiment of the present disclosure includes a coexistence enabler (CE) 200, a coexistence manager (CM) 300, a coexistence discovery and information server (CDIS) or a coexistence database (CDB) 400.

The coexistence manager (CM) 300 and the coexistence enabler (CE) 200 are logical entities defined for allowing different wireless systems or different wireless service providers operating in an unlicensed state to coexist. The CM 300 is an object which provides a policy or a guideline in relation to coexistence allowing different systems and different service providers having an interface with respect to a TVWS database and operating in the TVWS to coexist, and allocates resources to solve an interface problem between coexistence enablers (CEs) 200 connected thereto.

The coexistence enabler (CE) 200 has an interface with respect to a television band device (TVBD) network or device 100 and serves to transfer information or a command received from the CM 300 to the TVBD network or device 100. In the present disclosure, the STAs may perform the function of the CE 200, and a coexistence network structure in which a management entity such as the CM 300 exists as a higher object that may be able to control the plurality of CEs 200 will be handled.

The CE 200 receives information or a command in relation to coexistence from the CM 300. The CE 200 converts the received information and command into information or a command in a media-specific format and transfers the converted information or command to the TVBD network or device 100 for an operation of the TVBD network or device 100 required by a corresponding message. Similarly, information received from the TVBD network or device 100 may be converted into a message format defined in the coexistence system by the CE 200 and the transmitted to the CM 300. Since the CE 200 is disposed within the TVBD network or device 100, a service access point (SAP) and a primitive with an entity for managing the TVBD network or device 100 should be defined in order to allow the information or command for coexistence to be transferred.

The CM 300 may serve one or more CEs 200. The CM 300 may obtain required information from an external entity such as the TVWS database, the CEs 200 served by the CM 300 itself, or another CM 300. The CM 300 may transmit and receive information or a command message to and from the different CM 300 or transmit information or a command to the CE 200 served by the CM 300 itself. The CM 300 makes a coexistence decision based on the obtained information. Here, decision on an operation channel of the CE 200 served by the CM 300, a maximum transmission power value, and the like, may be included in the decision.

The TVBD network or device 100 may be an unlicensed user who uses a TV band, or the TVBD network or device 100 may be a device or a network. For example, the TVBD network or device 100 may be a device, such as an access point (AP) or a base station (BS), operating in a master mode. The TVBD network or device 100, the AP, or the BS, operating in the master mode, may communicate with the CM 300 for coexistence and manage and/or control devices operating in a slave mode.

The CDIS 400, having an interface with respect to the CM 300, obtains information regarding the CM 300 served by the CDIS 400 and the CE 200 served by the corresponding CM 300, e.g., geo-location information of the TVBD network or device 100 served by the CE 200, available channel list information obtained by the TVBD network or device 100 from the TVWS database, measurement results of the TVBD network or device 100, a list of CEs 200 served by the CM 300, and the like, from the CM 300 and manages the obtained information.

The CDIS 400 may calculate a neighbor relationship between the CMs 300 served by the CDIS 400 and that between the CEs 200. Namely, based on a particular TVBD network or device 100, the CDIS 400 may calculate a certain TVBD network or device 100 which is in an interference relationship with the particular TVBD network or device 100 and a CE 200 and a CM 300 that serve the certain TVBD network or device 100.

In order to use the coexistence service, the CE 200 establishes a connection with the CM 300 and registers itself to the corresponding CM 300. In this case, the CM 300 should establish a connection with a neighboring CM 300. The CM 300 manages CEs 200 registered to the CM 300, and provides a service for coexistence. Such a topology in which the CM 300 manages a plurality of CEs 200 and makes a decision for coexistence is called a centralized topology. In the centralized topology, the CM 300 is a decision maker, so the CD 200 follows the decision made by the CM 300.

Hereinafter, each element of the coexistence system will be described in detail.

The CE 200 is connected to the CM 300 via an interface B1, the CM 300 is connected to the CDIS or CDB 400 via an interface B2, and the CM 300 is connected to another CM 200′ via an interface B3.

Also, the CE 200 is connected with the TVBD network or device 100 through an interface A. Here, the TVBD network or device 100 refers to a terminal that is able to use TV white space in the US Federal Communication Commission (FCC). The TVBD network or device 100 may be connected with the TVWS database 600 through an interface C.

The CE 200 may request information required for coexistence from the TVBD network or device 100 and obtain the corresponding information, and switch a reconfiguration switching request/command and control information received from the CM 300 to a TVBD-specific reconfiguration request/command and transmit the same to the TVBD network or device 100.

In order to solve the coexistence problem between TVBD networks, the CM 300 may have a function of discovering different CMs, a coexistence decision function of generating corresponding coexistence request/command and control information and providing the generated coexistence request/command and control information to the CE 200, and a function of supporting exchanging of information required for coexistence between CMs (this may include hierarchical and/or peer-to-peer decision making capabilities in disposing CMs).

Also, the CM 300 may have a function of selecting a representative CM by sharing information regarding CMs, a function of generating a coexistence whitespace map for effectively sharing frequency resources between different networks (to be described) and between different systems, and a function of assisting network operators in performing management in relation to TVWS coexistence.

The CM 300 may be implemented in an embedded form in a device such as an AP or a BS or may be implemented outside a device.

The CDIS/CDB 400 may be represented by a CDIS or a CDB according to functions. The CDIS/CB 400 may have a function of generating a coexistence whitespace map or a coexistence map in order to effectively share frequency resources between different networks and between different systems, a function of controlling a plurality of operators in performing management in relation to TVWS coexistence, and a function of electing a representative CM in order to reduce overhead between CMs and solve a coexistence problem.

Also, the CDIS/CDB 400 may perform a function of calculating a coexistence contour in order to search for neighboring networks and/or systems, a function of redirecting the coexistence whitespace map or the coexistence map according to the TVBD in order to solve the coexistence problem, a function of supporting searching for CMs by accelerating opening of an interface between CMs, and a function of collecting, coordinating (i.e., synthesizing or generalizing), and providing information that may be able to promote coexistence (this function includes a data storing and data processing).

In allocating resources, the CDIS/CDB 400 may omnipotently distribute resources, present, as an intermediary, the reference of priority among the CMs 300 and fine-tune resource selection of the respective CMs 300, or act as an external and heterogeneous network medium for sharing information among the CMs 300.

Meanwhile, the interface A is an interface between the CE 200 and the TVBD network or device 100. Information required for coexistence, a request for configuration/information for coexistence, a configuration/measurement/information response for coexistence, and different information, as necessary, may be provided from the TVBD network or device 100. reconfiguration request/command and control information (which corresponds to coexistence request/command and control information received from a CM), a request/command in relation to controlling a measurement value performed by the TVBD network or device 100, information regarding available resource, and different information, as necessary, may be provided from the CD 200 to the TVBD network or device 100.

The interface B1 is an interface between the CE 200 and the CM 300. Information (information obtained from the TVBD network or device 100) required for coexistence and any other information, as necessary, may be provided from the CE 200 to the CM 300. Coexistence request/command and control information and any other information, as necessary, may be provided from the CM 300 to the CE 200.

The interface B2 is an interface between the CM 300 and the CDIS/CDB 400. Information required for a coexistence map, information required for a neighbor set, information required for registration or unenrollment, information required for searching (obtained by a currently used CM), information required for coexistence (obtained by the currently used CM), any other information as necessary, and the like, may be provided from the CM 300 to the CDIS/CDB 400.

From the CDIS/CDB 400 to the CM 300, information provided for coexistence map, information provided for a neighbor set (or a neighbor list), information provided for a representative CM, information required for searching (obtained by another CM), information required for coexistence (obtained by the different CM), and any other information as necessary, and the like, may be provided.

The interface B3 is an interface between the CM 300 and another CM 300′. From the CM 300 to another CM 300′, information and a message required for searching and coexistence, information provided for registration/unregistration (from the CM to a representative CM or from a CM of a device to a CM of a server), information provided for a coexistence map (from the CM to a representative CM or from a CM of a server to a CM of a device), information required for policy exchange/negotiation, any other information as necessary, and the like, may be provided.

The interface C is an interface between the TVBD device 100 and the TVWS database 600. Information provided for an available channel may be provided from the TVWS database 600 to the TVBD network or device 100.

The interface D is an interface between the CM 300 and an operator management entity (OME) 700. Network operation information in relation to information (e.g., a limitation factor related to an operation of a spectrum policy/network) and any other information as necessary may be provided to the CM 300 through the interface D by the OME 700.

FIG. 2 is a schematic block diagram showing a coexistence system according to another embodiment of the present disclosure.

As can be seen from FIG. 2, the CE 200 and the CM 300 may be embedded in an AP and a BS, respectively.

Also, the CDIS/CDB 400 may be connected to the TVWS database 600. Through this connection, the CDIS/CDB 400 may receive white space information from the TVWS database 600.

FIG. 3 is a view showing an example of a disposition of the coexistence system according to an embodiment of the present disclosure.

As can be seen from FIG. 3, a network A and a network B exist vertically. Also, a communication system A, a communication system B, and a communication system C exist horizontally. The communication system A, the communication system B, and the communication system C use different wireless access schemes, namely, communication schemes, respectively. For example, the communication system A may be a system such as CDMA, GSM, CDMA-2000, WCDMA, LTE, LTE-Advanced, or IEEE 802.16. The system B may be a cellular system whose cell coverage is smaller than that of the communication system A. Or, the system B may be a system such as Wi-Fi. The system C may be a cellular system, e.g., a femto-cell, whose cell coverage is smaller than that of the system B. The communication system A, the communication system B, and the communication system C has a coexistence manager (CM), respectively.

Meanwhile, the communication system A, the communication system B, and the communication system C geographically coexist within the network A and coexist within the network B. In order for the communication system A, the communication system B, and the communication system C to coexist, the CDIS/CDB 400 may generate a coexistence map and transmit the CM of each of the communication system A, the communication system B, and the communication system C.

FIG. 4 shows an operation of the coexistence system according to an embodiment of the present disclosure.

As can be seen from FIG. 4, it is illustrated that the CM 300 is not installed in an AP and a BS, but this is merely illustrative and the CM 300 may be installed in the AP and the BS. Also, the CE 200 may be installed in the AP and the BS.

Meanwhile, the AP and the BS are registered to the CM 300 and the CDIS/CDB 400, respectively.

The CM also performs registration to the CDIS/CDB 400 and the TVWS database.

Meanwhile, the CDIS/CDB 400 may receive a channel list for a broadcast from the TVWS database 600. The channel list may be frequency information for a broadcast. Also, the channel list may include information regarding an operating channel of a broadcast and a transmit power limitation.

The CDIS/CDB 400 checks whether or not the BS and the AP coexist within a certain area by using location information of the BS and the AP and an available channel information. When the BS and the AP coexist, the CDIS/CDB 400 may calculate a coverage radius of the AP and the BS, allocate channels (or resources) or one or more frequency bands that may be used by the different types of access points, namely, the AP and the BS, located in the certain area based on the channel list, namely, the frequency information for a broadcast, generate the channels (or resources) or information regarding the bands, e.g., a coexistence map, and transmit the same.

FIG. 5 is a view showing another example of a disposition of the coexistence system according to an embodiment of the present disclosure.

As can be seen from FIG. 5, the CM or the CDIS/CDB 400 may coordinate to allow several APs to coexist in the wireless environment. The several APs may be connected to the CDIS/CDB 400 by using a physical connection such as the Internet.

The CDIS/CDB 400 may obtain channel information for a broadcast from the TVWS database 600 as mentioned above. Also, the CDIS/CDB 400 may obtain channel information, e.g., a broadcast channel set, for a broadcast in a particular geographical area. Also, the CDIS/CDB 400 may calculate a coexistence contour. In particular, the CDIS/CDB 400 may have a neighbor detection function in different systems operating at the TV broadcast white space or a TV broadcast frequency.

Also, as mentioned above, the CDIS/CDB 400 may generate a coexistence white space map or a coexistence map. Also, the CDIS/CDB 400 may provide common clock information. Also, the CDIS/CDB 400 may provide information for time synchronization between different systems.

The CDIS/CDB 400 may provide a parameter with respect to a radio range and an interference range of each device. The CDIS/CDB 400 may provide a parameter with respect to the foregoing coexistence contour. The CDIS/CDB 400 may identify neighbor network devices for the purpose of coexistence between different systems. The CDIS/CDB 400 may provide information regarding transmission power of each network, an antenna height, and any other physical parameters.

FIGS. 6A and 6B are views showing an operation of a CDIS/CDB 400.

As can be seen from FIG. 6A, a first CM CM1 and a second CM CM2 exist. The first CM CM1 and the second CM CM2 are connected to the TVWS DB 600 and the CDIS/CDB 400, respectively. The first CM CM1 and the second CM CM2 receive location information and frequency information for a broadcast, e.g., information regarding a whitespace map, from the TVWS DB 600. The whitespace map may refer to information regarding an empty frequency band not used by a broadcast service provider in VHF and UHF frequency bands distributed as TV broadcast bands.

Meanwhile, the CDIS/CDB 400 may be connected to the TVWS DB 600 and receive the frequency information for a broadcast, e.g., the whitespace map, from the TVWS DB 600. As mentioned above, the CDIS/CDB 400 may generate a coexistence whitespace map or a coexistence map based on the frequency information for a broadcast, e.g., the whitespace map. The CDIS/CDB 400 may transfer the generated coexistence whitespace map (CWM) or the coexistence map to the first CM CM1 and the second CM CM2.

Meanwhile, as can be seen from FIG. 6B, the first CM CM1 and the second CM CM2 are connected to the TVWS DB 600. The TVWS DB 600 may be connected to the CDIS/CDB 400.

The CDIS/CDB 400 may transfer the foregoing CWM or the coexistence map to the TVWS DB 600, and the TVWS DB 600 may transfer the received CWM or the coexistence map to the first CM CM1 and the second CM CM2. In this case, the TVWS DB 600 may transfer the received CWM or the coexistence map under the assumption that it is frequency information for a broadcast, e.g., the whitespace map.

Alternatively, the TVWS DB 600 may transfer the frequency information for a broadcast, e.g., the whitespace map, as well as the received CWM or the coexistence map, to the first CM CM1 and the second CM CM2. In this case, when the first CM CM1 and the second CM CM2 receive the CWM, the coexistence map, and the frequency information for a broadcast, e.g., the whitespace map, the first CM CM1 and the second CM CM2 may select and use appropriate one or more of them.

FIG. 7 is a view showing coexistence contours.

As can be seen from FIG. 7, the network A, the network B, and the network C exist in proximity. Coexistence contours of the respective networks are illustrated by solid lines and distances between the respective networks are illustrated by dotted lines. The coexistence contours are determined by the characteristics of the respective networks. Meanwhile, the distance between the respective networks may be determined by characteristics with different networks. As can be seen from FIG. 8, the coexistence contours between the network A and the network B are almost in contact, and the coexistence contours between the network A and the network C overlap with each other.

FIG. 8 is a view showing an example of a coexistence whitespace map (CWM) or a coexistence map in the environment of FIG. 7.

As shown in a right upper portion of FIG. 8, it is assumed that channels 1 to 6 exist. In this case, it is assumed that channels 1 and 2 are channels used for a broadcast according to the frequency information for a broadcast, e.g., the whitespace map.

The CDIS/CDB 400 transmits the CWM or the coexistence map indicating that the channel 4 is an idle channel to the network A. Accordingly, when the network A determines to use the channel 4, the CDIS/CDB 400 transmits the CWM or the coexistence map indicating that the channel 3, the channel 5, and the channel 6 are idle channels to the network B. Accordingly, when the network B determines to use, for example, the channel 6, the CDIS/CDB 400 may transmit the CWM or the coexistence map indicating that the channel 3 and the channel 5 are idle channels to the network C.

In this manner, the CDIS/CDB 400 transmits the CWM or the coexistence map to the networks A, B, and C, to thus allow the networks A, B, and C to coexist in the wireless environment.

In the coexistence system, the CM 300 determines an operating channel of the CEs 200 served by the CM 300 itself. The CM 300 may arbitrarily distribute and allocate an operating channel in a TV band, or effectively allocate an operating channel by using an interference relationship between the TVBD networks or devices 100 served by the respective CEs and an available channel list. The TVBD network or device 100 served by the CE 200 may operate in an intersection area of the operating channel allocated by the CE and an available channel. In case in which the TVBD network or device 100 wants to move to a channel other than the operating channel allocated to the CE 200 by the CM 300, the TVBD network or device 100 cannot change the operating channel independently and the CM 300 must newly change the allocation of the operating channel.

In order to solve a coexistence problem in a coexistence system, the CM 300 is required to obtain a neighbor relationship between CEs served by the CM 300 itself. Namely, the CM 300 checks a TVBD network or device, which is served by a CE of another CM and is in an interference relationship with the TVBD network or device of the CE served by the CM 300 itself. And then, the CM 300 allocates, to the TVBD network or device of the CE served by the CM 300, radio resources different from radio resources allocated to the TVBD network or device in the interference relationship with the TVBD network or device of the CE served by the CM 300.

Before determining an operating channel of the CE, the CM may access the CDIS 400 to request a neighbor list in order to obtain an interference relationship between CEs or between TVBD networks or devices served by the CM 300, or between a TVBD network or device served by the CM 300 and a TVBD network or device served by a CE of another CM. At this time, the CM 300 transmits a neighbor list request message to the CDIS 400.

Table 1 below shows a frame structure of the neighbor list request message according to an embodiment of the present invention disclosed in the present disclosure.

TABLE 1 Header Name Data type Description SourceIdentifier COEX_ID CDIS identifier DestinationIdentifier COEX_ID CM identifier InformationType COEX_INFO_TYPE Message type DialogTocken Integer Message sequence number Payload Information element (IE) Data type Description Note: Following IEs are repeated for each CM CMIdentifier COEX_ID CM may request a neighbor list of another CM served by it Note: Following IEs are repeated for each registered CE CEIdentifier COEX_ID Registered CE Note: Following IEs are repeated for each TVBD network or device TVBDType TVBD_TYPE TVBD network or device type Geolocation GEO_LOC Registered location information Note: Following IEs are repeated for each channel of TVBD ChannelNumber Integer Channel number MaximumPowerLevel Real Power limitation

With reference to Table 1, the neighbor list request message includes a header and a payload. The header includes an identifier (SourceIdentifier) of the CM 300 that transmits the request for a neighbor list, an identifier (DestinationIdentifier) of the CDIS/CDB 400 that receives the request for a neighbor list, a message type for discriminating a frame of the neighbor list request message from another coexistence frame (InformationType), and a sequence number (DialogTocken) of a message.

The payload includes an identifier (CMIdentifier) of a CM that wants to obtain the neighbor list, an identifier (CEIdentifier) of the CE served by the CM that wants to obtain the neighbor list, a type (TVBDType) of the TVBD network or device, location information (Gelocation) of the TVBD network or device indicated by 3D coordinates, a channel number (ChannelNumber) representing a TV band that can be used by the TVBD network or device, as a channel number indicated on an available channel list obtained from the TVWS DB 600, and a maximum power level (MaximumPowerLevel) of the TVBD network or device 100.

Here, in case in which a plurality of CMs exist in the coexistence system, the identifier (CMIdentifier) of the CM that wants to obtain the neighbor list may be an identifier of the CM 300 that transmits the request for a neighbor list or another CM recognized by the CM 300.

When a plurality of CMs want to obtain the neighbor list, the identifier (CM Identifier) of the CMs that want to obtain the neighbor list is repeated for the respective CMs. Also, in case in which CM that wants to obtain the neighbor list serves a plurality of CEs, the identifier (CEIdentifier) of the CEs served by the CM that wants to obtain the neighbor list is repeated for each CE. Also, when the CE serves a plurality of TVBD networks or devices, the type (TVBDType) of the TVBD network device and the location information (Geolocation) of the TVBD network or device are repeated for each TVBD network or device.

Also, when there are a plurality of available channels of the TVBD network or device, the channel number (ChannelNumber) and maximum power level (MaximumPowerLevel) are repeated for each available channel.

Meanwhile, the type (TVBDType) of the TVBD network or device may be defined as shown in Table 2 below.

TABLE 2 Device type Description 0-1 Reserved 2 Fixed device 3 Personal/portable device 4-7 Reserved

TABLE 3 Latitude Latitude Latitude Longitude Longitude Item Resolution Fraction Integer Resolution Fraction bit 6 25 9 6 25 Longitude Altitude Altitude Altitude Altitude Item Integer Type Resolution Fraction Integer bit 9 4 6 8 22

The channel number (ChannelNumber) may be a TV channel number or an operating channel of a TVBD network or device. In case of a 802.11 system, an operating channel of a TVBD network or device may be represented by a combination of an operating class and a channel number.

When the CDIS 400 receives the neighbor list request message from the CM 300, the CDIS 400 calculates a requested neighbor list of the CM among the CMs served by the CDIS 400. In this case, the neighbor information may include information regarding a CE of the CM 300, a requested CE and a requested TVBD network or device located in an interference area with a TVBD network or device.

For example, when only a single CM exists in the coexistence system, since there is no CM in a neighbor relationship, the neighbor information may be the requested neighbor information regarding CEs served by the CM. When a plurality of CMs exist in the coexistence system, the neighbor information may include the requested neighbor information regarding CEs served by the CM and a requested CE and TVBD network or device served by another CM existing in an interference area with the CE served by the CM.

The CDIS 400 transmits a neighbor list response message including the neighbor information to the CM 300.

Table 4 below shows a frame structure of the neighbor list response message according to an embodiment disclosed in the present disclosure.

TABLE 4 Header Name Data type Description SourceIdentifier COEX_ID CDIS identifier DestinationIdentifier COEX_ID CM identifier InformationType COEX _INFO_TYPE Message type DialogTocken Integer Message sequence number Payload Information element Data type Description Note: Following IEs are repeated for each CM CMIdentifier COEX_ID CM may request a neighbor list of another CM served by it Note: Following IEs are repeated for each registered CE CEIdentifier COEX_ID Registered CE Note: Following IEs are repeated for each TVBD network or device TVBDAddress OCTET(6) MAC address of TVBD Note: Following IEs are repeated for each channel having neighbor TVBD ChannelNumber Integer Channel number Note: Following IEs are repeated for each neighbor TVBD network or device NeighborCM COEX_ID Neighbor CM identifier NeighborCE COEX_ID Neighbor CE identifier NeighborTVBDAddress OCTET(6) MAC address of neighbor TVBD network or device

With reference to Table 4, the neighbor list response message includes a header and a payload. The header includes an identifier (SourceIdentifier) of the CM 300 that transmits the request for a neighbor list, an identifier (DestinationIdentifier) of the CDIS/CDB 400 that receives the request for a neighbor list, a message type for discriminating a frame of the neighbor list response message from a different coexistence frame (InformationType), and a sequence number (DialogTocken) of a message.

The payload includes an identifier (CMIdentifier) of a CM that wants to obtain the neighbor list (The CMIdentifier is identical to the CMIdentifier of the neighbor list request message), an identifier (CEIdentifier) of the CE served by the CM that wants to obtain the neighbor list, a unique number (TVBDAddress) of a TVBD network or device served by the CE indicated by the CEIdentifier, a TV channel number (ChannelNumber) (The CM 300 may receive a neighbor list from the CDIS 400 by the TV channel number (ChannelNumber). Thus, the CM 300 may obtain information regarding a TVBD network or device in a neighbor relationship with a TVBD network or device with respect to each channel and information regarding the CE 200 and the CM 300 serving the TVBD network and device), an identifier (NeighborCM) of the CM in a neighbor relationship with the TVBD network or device indicated by TVBDAddress, an identifier (NeighborCE) of the CM in a neighbor relationship with the TVBD network or device indicated by TVBDAddress, and a unique number (NeighborTVBDAddress) of the TVBD network or device in a neighbor relationship with the TVBD network or device indicated by the TVBDAddress.

When a plurality of CMs want to obtain the neighbor list, the identifier (CMIdentifier) of the CMs that want to obtain the neighbor list is repeated for the respective CMs. Also, in case in which CM that wants to obtain the neighbor list serves a plurality of CEs, the identifier (CEIdentifier) of the CEs served by the CM that wants to obtain the neighbor list is repeated for each CE.

Also, when the CE serves a plurality of TVBD networks or devices, the type (TVBDType) of the TVBD network device and the location information (Geolocation) of the TVBD network or device are repeated for each TVBD network or device. Also, when the TVBD network or device has a plurality of channels, the channel number (ChannelNumber) is repeated for each channel.

Also, when a plurality of TVBD network and devices are in a neighbor relationship with the TFBD network or device indicated by the TVBDAddress, the identifier (NeighborCM) of the CM in a neighbor relationship with the TVBD network or device indicated by the TVBDAddress, the identifier (NeighborCE) of the CM in a neighbor relationship with the TVBD network or device indicated by the TVBDAddress, and a unique number (NeighborTVBDAddress) of the TVBD network in a neighbor relationship with the TVBD network or device indicated by the TVBDAddress are repeated for each TVBD network or device.

The neighbor list response message may include information regarding a CE 200 served by the CM 300 who has requested the neighbor list through the neighbor list request message and a neighbor CE 200 of the TVBD network or device, and when a neighbor TVBD network or device exists in the coexistence system, the neighbor list response message may include a neighbor TVBD network or device of each TVBD network or device, a CE 200 served by the neighbor TVBD network or device, and a CM 300.

FIG. 9 is a flow chart illustrating a process of searching for a neighbor according to an embodiment of the present disclosure.

The CDIS 400 calculates a neighbor list based on location information of every TVBD network or device existing in a coexistence system and information regarding an available channel list. The location information of every TVBD network or device existing in the coexistence system and the information regarding the available channel list may be transferred during the process in which the CM 300 registers to the CDIS 400, or may be obtained when each CM 300 re-transmits the neighbor list request message as the location information of each TVBD network or device served by each CM 300 or the available channels are updated.

A neighbor searching process of the CDIS 400 is as follows. First, a connection is established between the CDIS 400 and the CM 300 through the interface B2. The CM 300 transmits the neighbor list request message to the CDIS 400 by using the frame as shown in Table 1. The CDIS 400 may obtain an interference relationship between respective TVBD networks or devices by using the type (TVBDType) of each TVBD network or device, location information (Geolocation) of each TVBD network or device, and a channel number (ChannelNumber) signifying a TV band that may be used by each TVBD network or device (step S120). The CDIS 400 may obtain a neighbor list based on the obtained interference relationship between the respective TVBD networks or devices. The CIDS 400 may transmit a neighbor list response message to the CM 300 by using the frame as shown in Table 4 (step S130).

The CDIS 400 may determine a channel for which a neighbor relationship exists between respective networks or devices in consideration of a physical distance (coexistence contour) between respective TVBD networks or devices and a list of available channels of the respective TVBD networks or devices.

The CM 300 receives the neighbor list response message from the CDIS 400, and then, when there is a neighbor TVBD network or device, the CM 300 checks an operating channel from a CM that manages the corresponding neighbor TVBD network or device, and determines an operating channel of the TVBD network or device in consideration of the operating channel (e.g., such that the operating channels are not overlapped). Such determination of the operating channel may be performed by the CE 200 or the TVBD network or device 100.

FIG. 10 is a view showing information regarding available channels of a television band device (TVBD) network or device according to an embodiment of the present disclosure.

With reference to FIG. 10, the CE A is a fixed device (e.g., in case in which the device type in Table 1 is 2), in which a TV exists in a TV channel 3. An available channel of the CE A may be a channel 1 and a channel 5.

An embodiment in which the CE A and the CE B are served by the same CM in the coexistence system will be described in detail with reference to FIG. 11. Also, an embodiment in which the CE A and the CE B are served by different CMs in the coexistence system will be described in detail with reference to FIG. 12.

FIG. 11 is a conceptual view showing a process for searching for a neighbor according to a first embodiment of the present disclosure.

In the first embodiment, the CM A may serve the CE A and the CE B having channel information as shown in FIG. 11.

The CM A may request a neighbor list from the CDIS 400. The CDIS 400 may calculate an interference range based on location information (geolocation) of each CE, and determine that the CE A and CE B are in a neighbor relationship.

With reference back to FIG. 10, in the case of channel 1 to channel 4, since the CE A and CE B are of different device types from those that can be used in the available channels of the CE A and CE B, so they may select one of their available channels to use, respectively, regardless of interference. However, since the channel 5 is a channel available for both of the CE A and the CE B, the CE A and the CE B are in a neighbor relationship in the channel 5.

Table 5 below shows an example of a frame of a neighbor list response message according to neighbor searching according to the first embodiment disclosed in the present disclosure.

TABLE 5 Header Name Data type Description SourceIdentifier COEX_ID CDIS identifier DestinationIdentifier COEX_ID CM identifier InformationType COEX_INFO_TYPE Message type DialogTocken Integer Message sequence number Payload Information element (IE) Data type Data value Note: Following IEs are repeated for each CM CMIdentifier COEX_ID CM A CEIdentifier COEX_ID CE A ChannelNumber Integer 5 TVBDAddress OCTET(6) CE B

A data value of the identifier (CMIdentifier) (it is identical to the CM identifier of the neighbor list request message) of the CM that wants to obtain a neighbor list is the CM A, and a data value of the identifier (CE Identifier) of the CE served by the CM that wants to obtain the neighbor list is the CE A.

The data value of the TV channel number (ChannelNumber) is 5, and a data value of the identifier (NeighborCE) of the CE in a neighbor relationship with the CE A indicated by the TVBDAddress is the CE B.

FIG. 12 is a conceptual view showing a process for searching for a neighbor according to a second embodiment of the present disclosure.

In the second embodiment, the CM A may serve the CE A having the channel information illustrated in FIG. 10, and the CM B may serve the CE B having the channel information illustrated in FIG. 10.

The CM A may request a neighbor list from the CDIS 400. The CDIS 400 may calculate an interference range based on the location information (geolocation) of each CE, and determine that the CE A and CE B are in a neighbor relationship.

With reference back to FIG. 10, in the case of channel 1 to channel 4, since the CE A and CE B are of different device types from those that can be used in the available channels of the CE A and CE B, so they may select one of their available channels to use, respectively, regardless of interference.

However, since the channel 5 is a channel available for both of the CE A and the CE B, the CE A and the CE B are in a neighbor relationship in the channel 5. When the CE A and the CE B simultaneously use the channel 5, the CE A and the CE B are interfered with each other.

Table 6 below shows an example of a frame of a neighbor list response message according to neighbor searching according to the second embodiment disclosed in the present disclosure.

TABLE 6 Header Name Data type Description SourceIdentifier COEX_ID CDIS identifier DestinationIdentifier COEX_ID CM identifier InformationType COEX _INFO_TYPE Message type DialogTocken Integer Message sequence number Payload Information element (IE) Data type Data value Note: Following IEs are repeated for each CM CM identifier COEX_ID CM A CE identifier COEX_ID CE A ChannelNumber Integer 5 CE identifier COEX_ID CE B CM identifier COEX _ID CM B

A data value of the identifier (CMIdentifier) (it is identical to the CM identifier of the neighbor list request message) of the CM that wants to obtain a neighbor list is the CM A, and a data value of the identifier (CE Identifier) of the CE served by the CM that wants to obtain the neighbor list is the CE A.

The data value of the TV channel number (ChannelNumber) is 5, a data value of the identifier (NeighborCE) of the CE in a neighbor relationship with the CE A indicated by the CEidentifier is B, and a data value of the identifier (NeighborCM) of the CM in a neighbor relationship with the CE A indicated by the CMidentifier is B.

FIG. 13 is a flow chart illustrating a process of allocating resources by a coexistence manger (CM) according to embodiments of the present disclosure.

The first CM CM1 requests a neighbor list of a first TVBD network or device served by a first CM CM1 from the CDIS 400 (step S110). The CDIS 400 calculates a neighbor list of the first TVBD network or device served by the first CM CM1 (step S120), and transmits the calculated neighbor list to the first CM CM1 (step S130).

The first CM (CM1) may request information from the second CM CM2 that serves a second TVBD network or device included in the neighbor list received from the CDIS 400 or negotiate (step S140) to determine an operating channel of the TVBD network or device served by the first CM CM1 (step S150).

For example, the first CM may receive information regarding an operating channel allocated to the second TVBD network or device from the second CM CM2, and allocate a channel, which has not been allocated as an operating channel to the second TVBD network or device among available channels of the first TVBD network or device, as an operating channel of the first TVBD network or device.

FIG. 14 is a flow chart illustrating a process of updating a neighbor list according to embodiments of the present disclosure.

When location information or an available channel list of a CE or a TVBD network or device served by the first CM CM1 is updated, the first CM CM1 transmits a neighbor list request including updated information to the CDIS 400 (step S210).

The CDIS 400 calculates again a neighbor list based on the updated information (step S220) and transmits the updated neighbor list to the first CM CM1 (step S230). In this case, the CDIS 400 may designate a particular type to indicate whether or not the corresponding neighbor light has been changed.

In case in which the CDIS 400 serves a plurality of CMs, when information of a particular CM CM1 is updated and a neighbor list request is received, a neighbor relationship newly calculated based on the updated information may include a CE or a TVBD network or device of another CM CM3. In this case, the CDIS 400 may transmit the changed neighbor information to the CM whose neighbor list has been changed without a particular request (unsolicited response) (step S230) or transmit a changed neighbor list to the corresponding CM CM3 according to a request (announcement) (steps S240 and S250).

FIG. 15 is a flow chart illustrating a process for receiving occupied channel information and interference level information from the TVBD network or device 100 by the CM 300 according to an embodiment of the present disclosure.

The TVBD network or device 100 may transmit the occupied channel information and interference level information to the CM 300 through a measurement message. In this case, the TVBD network or device 100 may transmit a measurement frame format to the CM 300 according to a request from the CM 300.

Namely, the CM 300 transmits a measurement request (measurement_request) to the CE 200 (step S312), and the CE 200 transmits the received measurement request to the TVBD network or device 100 (step S314). Also, in response to the measurement request, the TVBD network or device 100 transmits a measurement report to the CE 200 (step S316), and the CE 200 transmits the received measurement report to the CM 300 (step S318).

FIG. 16 is a flow chart illustrating a process for receiving occupied channel information and interference level information from the TVBD network or device 100 by the CM 300 according to another embodiment of the present disclosure.

Meanwhile, the TVBD network or device 100 may periodically transmit a measurement frame format to the CM 300. Namely, the TVBD network or device 100 periodically transmits the measurement report to the CE 200 (step S322), and the CE 200 transmits the received measurement report to the CM 300 (step S324).

The measurement report frame format may be defined as shown in Table 7 below.

TABLE 7 Measurement Information Coexistence Information report Element frame header type elements octet 8 1 Variable

The coexistence frame header identifies a frame. The value of the information type field may be set to be 3 (measurement request). The measurement request elements field may include one or more measurement request elements. In a single measurement request frame, the number and length of the measurement request elements may be limited by the size of a maximum allowed coexistence protocol data unit (CXPDU). The measurement request elements may include a request for performing a designated measurement operation of the TVBD network or device 100 that receives the measurement request.

The measurement request element frame format may be defined as shown in Table 8 below.

TABLE 8 Information Measurement Measurement element Length type request Octet 1 1 Variable

The measurement type field may be defined as shown in Table 9 below.

TABLE 9 Measurement type Description 0 Reserved 1 Interference Level 2 Occupied Channel Information 3-7 Reserved

In the measurement request element, the measurement type may indicate an interference level. The measurement request field corresponding to the interference level request element may be defined as shown in Table 10 below.

TABLE 10 Information Measurement Measurement TV channel element Start Time Duration numbers Octet 2 1 Variable

The measurement start time field is set to be a time at which a requested measurement starts. The value 0 indicates that the requested measurement immediately starts. The measurement duration field may be set as a duration time of the requested measurement expressed by time units (TUs). The TV channel numbers indicate TV channel numbers to which the measurement request is applied. The channel numbers may be determined to be different in each country or area.

The measurement report frame format may be defined as shown in Table 11 below.

TABLE 11 Information Coexistence Information Measurement element frame header type report elements Octet 8 1 Variable

The coexistence frame header identifier a frame. A value of the information type field of a measurement report may be set to be, for example, 4. The measurement report elements field may include one or more measurement report elements. The number and length of the measurement report elements in a single measurement report frame may be limited by a maximum allowed CXPDU size.

The measurement report elements frame format may be defined by Table 12 shown below.

TABLE 12 Information Measurement Measurement element Length type report Octet 1 1 Variable

The measurement type field may be defined as shown in Table 3 above. In the measurement report element, the measurement type may indicate an interference level. The measurement report field corresponding to the interference level report element may be defined as shown in Table 13 below.

TABLE 13 Actual Measuring Interference Information Measurement Measurement TVBD Level element Start Time Duration Address Report Octet 8 2 6 Variable

The actual measurement start time field is set as a time at which a TVBD measurement starts. The measurement duration field is set as a duration time in which a TVBD report expressed by time units (TUs) is measured. The measuring TVBD address field is set as a MAC address of the TVBD network or device 100 that has actually performed measurement. The interference level report field may be periodically repeated. The interference level report field may indicate the detected TVBD network or device 100.

The measurement type in the measurement report element may indicate occupied channel information. The measurement report field corresponding to the occupied channel information may be defined as shown in Table 14 below.

TABLE 14 Actual Occupied Measurement Measuring Channel Information Start Measurement TVBD Information element Time Duration Address Report Octet 8 2 6 Variable

The occupied channel information report may be defined as shown in Table 15 below.

TABLE 15 Device Type Description 0 Reserved 1 Channel Number 2 Power 3-7 Reserved

The actual measurement start time field may be set as a time at which a TVBD measurement starts. The measurement duration field may be set as a duration time in which the TVBD report expressed by time units (TUs) is measured. The channel number may be set as a channel number used by the TVBD user.

FIG. 17 is a flow chart illustrating a process of discovering a neighbor set of the TVBD network or device 100 by the CM 300 according to an embodiment of the present disclosure.

First, the CDIS 400 may receive neighbor information, timing information, resource information, an interference level, and the like, from the TVBD network or device 100 or the CM 300, calculate a neighbor set, and transfers the calculated neighbor set to the CM 300 (step S410).

The CM 300 transmits a request for occupied channel information of the neighbor TVBD network or device 100′ including the neighbor set to the neighbor CM 300′ (step S420). The CM 300 receives the occupied channel information of the neighbor TVBD network or device 100′ from the neighbor CM 300′ (step S430).

The CM 300 compares an available channel of the TVBD network or device 100 and the occupied channel of the neighbor TVBD network or device 100′. And then, the CM 300 checks a channel included in the occupied channel of the neighbor TVBD network or device 100′ among channels included in the available channels of the TVBD network or device 100 (overlap channel(s) is/are calculated). The CM 300 generates a channel table (or a priority table) in which a channel included in occupied channels of the neighbor TVBD network or device 100′ and a channel not included in the occupied channels of the neighbor TVBD network or device 100′, among channels included in available channels of the TVBD network or device 100, have different priority levels (step S440).

Here, among the channels included in the available channels of the TVBD network or device 100, a channel included in the occupied channel of the neighbor TVBD network or device 100′ may have a priority level lower than that of a channel not included in the occupied channel of the neighbor TVBD network or device 100′. The channel table (or priority table) may be divided into a table based on occupied channel information and a table based on the number of TVBD networks or devices 100 served by each CM 300. Alternatively, a table incorporating (or merging) the two types of tables may be configured.

The CM 300 transfers the generated channel table (or the priority table) to the TVBD network or device 100 (step S450).

A neighbor discovery information frame format that may be used in the process of discovering a neighbor set may be defined as shown in Table 16 below.

TABLE 16 Neighbor Information Coexistence Information discovery element frame header type information Octet 8 1 Variable

The coexistence frame header identifies a frame. The information type field may be set to be, for example, 3 (measurement request). The neighbor discovery information elements include one or more neighbor discovery information elements. In a single neighbor discovery information frame, the number and length of the neighbor discovery information elements are limited by the size of a maximum allowed CXPDU.

The neighbor discovery information element format may be defined as shown in Table 17 below.

TABLE 17 Neighbor Neighbor discovery discovery Information information information element Length Table request Octet 1 1 Variable

Neighbor discovery information field may be defined as shown in Table 18 below.

TABLE 18 Measurement Type Description 0 Reserved 1 Neighbor discovery information 2-7 Reserved

The neighbor discovery information table element may indicate occupied channel information. The neighbor discovery information corresponding to the neighbor discovery information request element may be defined as shown in Table 19 below.

TABLE 19 Information Occupied TV TV channel element channel numbers Octet 2 variable

The TV channel numbers indicate TV channel numbers to which the neighbor discovery information request is applied. Channel numbers are defined to be different in each country or area.

The neighbor discovery information request element may indicate occupied channel information of the CM 300 (or the neighbor TVBD network or device 100). The neighbor discovery request element field corresponding to the neighbor discovery information request element may be defined as shown in Table 20 below.

TABLE 20 Information Neighbor CM Occupied TV element ID channel Octet 2 2

FIG. 18 is a flow chart illustrating a process of switching a service by the TVBD network of device 100 or the CM 300 according to an embodiment of the present disclosure.

In the coexistence system, two types of services may be provided. A first service (management service) may be a service in which the CM 300 determines an available channel of the TVBD network or device 100 on the basis of various types of information such as neighbor information, timing information, resource information, interference level information, and the like, and transfers the determined available channel information to the TVBD network or device 100 and manages the same.

A second service (discovery/information service) may be a service in which the TVBD network or device 100 receives a neighbor set from the CIDS 400, receives an available channel list from the TVWS DB 600, and determines an available channel. Switchover between the first and second services may be made by the TVBD network or device 100 or the CM 300. Also, the TVBD network or device 100 may receive service information from the CM 300 and select any one of the first and second services as a service of the coexistence system on the basis of the received service information.

The TVBD network or device 100 may determine whether to switch a service on the basis of the available channel information received from the CM 300. When there is no available channel which is required (e.g., when a channel having a sufficient size cannot be secured although a plurality of adjacent channels are merged), the TVBD network or device 100 may determine switching from the first service to the second service. In this case, the TVBD network or device 100 transfers a service changing request to the CE 200 (step S512), and the CE 200 transmits the service changing request to the CM 300 (step S514). In response to the service changing request, the CM 300 transmits first service information (C-MAP) or second service information (TVBD neighbor information) to the CE 200 (step S516), and the CE 200 transfers the received service information to the TVBD network or device 100 (step S518).

FIG. 19 is a flow chart illustrating a process of switching a service by the_TVBD network of device 100 or the CM 300 according to another embodiment of the present disclosure.

The CM 300 generates a service switch command (Service_switch_command) on the basis of various types of information such as neighbor information, timing information, resource information, interference level information, and the like, received from the CDIS/CDB 400 and the TVBD network or device 100 (step S522) and transmits the generated service changing command to the CE 200 (step S524). The CE 200 transfers the received service changing command to the TVBD network or device 100 (step S526).

The service changing request frame format may be defined as shown in Table 21 below.

TABLE 21 Service changing Information Coexistence Information Dialog request element header Type Token element Octet 8 1 Variable

The coexistence header identifies a frame. The information type field may be set to be 9 (Service changing request frame) indicating a service changing request frame. The service changing request element format may be defined as shown in Table 22 below.

TABLE 22 Information Command Command element Length Type request Octet 1 1 Variable

The command type field is defined as shown in Table 23 below.

TABLE 23 Command Type Description 0 Reserved 1 Service Changing 2-7 Reserved

In the service changing command request element, the command type may indicate service switching. The service changing request field corresponding to the service changing command request element may be defined as shown in Table 24 below.

TABLE 24 Information TVBD Service element Address/CM ID Type Octet 6 variable

Length is a variable value subject to the length value of the service type field.

The service changing response frame format may be defined as shown in Table 25 below.

TABLE 25 Service changing Information Coexistence Information Dialog response element header Type Token element Octet 8 1 Variable

The coexistence header identifies a frame. The information type field is set to be 10 (service changing response frame) indicating a service changing response frame. The service changing response element format is defined as shown in Table 26 below.

TABLE 26 Information Command Command element Length Type response Octet 1 1 Variable

The command type field is defined as shown in Table 23 above.

In the service changing command response element, the command type may indicate service switching. The service changing response field corresponding to the service changing command response element may be defined as shown in Table 27 below>

TABLE 27 Information element Status Code Octet 1

The status code field indicates success or failure of a requested operation. A length of the status code field may be 1. An allocated status code may be defined as shown in Table 28 below.

TABLE 28 Measurement Type Description 0 Reserved 1 Reserved 2 Success 3 Unspecified failure 4-255 Reserved

FIG. 20 is a flow chart illustrating a process of selecting a service by the_TVBD network of device 100 according to another embodiment of the present disclosure.

The CM 300 transmits a C-MAP (Coexistence MAP) for a first service and neighbor information for a second service to the CE 200 (step S532), and the CE 200 transfers the received neighbor information to the TVBD network of device 100 (step S534). The TVBD network of device 100 selects a service on the basis of the received neighbor information.

The service switching frame format is defined as shown in Table 29 below.

TABLE 29 Information Coexistence Information Service switching element frame header type request elements Octet 8 1 Variable

The coexistence frame header identifies a frame. A value of the information type field is set to be 3 (Service switching request). The service switching request elements field may include one or more service switching request elements. In a single measurement request frame, the number and a length of the service switching request elements may be limited by the size of a maximum allowed CXPDU. The service switching request element may include a request for performing a designated service switching operation of the TVBD network or device 100 that receives the service switching request.

The service switching request element format may be defined as shown in Table 30 below.

TABLE 30 Information Service Service switching element Length type request Octet 1 1 Variable

The service type field may be defined as shown in Table 31 below.

TABLE 31 Measurement Type Description 0 Reserved 1 Service switching 2-7 Reserved

The service type field may be defined as shown in Table 32 below.

TABLE 32 Management Discovery/Information Information Service Service element information information Octet 2 2

The management service sub-element field may be defined as shown in Table 33 below.

TABLE 33 Sub- Available Information element Received Channel element ID Length Power Numbers Octet 1 1 1 Variable

The discovery/information service sub-element field may be defined as shown in Table 34 below.

TABLE 34 Information Sub- CM Neighbor TVBD element element ID Length ID information Octet 1 1 1 Variable

The service switching request element field may be defined as shown in Table 35 below.

TABLE 35 Information Service Changing element Service Type command Octet 2 2

FIG. 21A is a view showing semantics of a service primitive of a coexistence service changing request according to an embodiment of the present disclosure.

COEX_Servicechanging.request is used by a COEX user in order to change a service type. Parameters of the COEX_Servicechanging.request are defined as shown in Table 36 below.

TABLE 36 Name Data type Description DestinationIdentifier COEX_ID It identifies a local COEX entity or a remote COEX entity as destination of the request. ServiceType SERVICETYPE_ID Service type

COEX_Servicechanging.request is generated by the COEX user in order to change a service type. If a destination of the request is a local COEX entity itself, the local coexistence (COEX) entity responds by COEX_Servicechanging.confirm. If the destination of the request is a remote COEX entity, the local COEX entity may generate a Servicechanging Request message corresponding to the remote COEX entity.

FIG. 21B is a view showing semantics of a service primitive of a coexistence service change notification according to an embodiment of the present disclosure.

COEX_Servicechanging.indication is used by a COEX entity in order to notify the COEX user on a reception of a service switching report (Servicechanging Request) message from a peer COEX entity. A parameter of COEX_Servicechanging.indication is defined as shown in Table 37 below.

TABLE 37 Name Data type Description SourceIdentifier COEX_ID It identifies an invoker of a primitive which may be a local COEX entity or a remote COEX entity. ServiceType SERVICETYPE_ID Service type

The parameter of COEX_Servicechanging.indication is used by the COEX entity in order to notify the COEX user on a reception of a COEX_Servicechanging.request message when the COEX_Servicechanging.request message is received. When the indication is received, the COEX user responds by a COEX_servicechanging.reponse primitive.

FIG. 21C is a view showing semantics of a service primitive of a coexistence service changing response according to an embodiment of the present disclosure.

The COEX_Servicechanging.response is used by the COEX user in order to convey local service changing information (servicechanging information) to the COEX user who has invoked the service changing request (servicechanging request). The parameter of COEX_Servicechanging.response is defined as shown in Table 38 below.

TABLE 38 Name Data type Description DestinationIdentifier COEX_ID It identifies remote COEX entity as destination of this response. ResultCode Enumeration It reports the outcome of a request.

The parameter of COEX_Servicechanging.response is used by the COEX user in response to the received COEX_Servicechanging.indication. When the response is received, the COEX entity may generate a corresponding COEX_servicechanging.report message and send the generated COEX_servicechanging.report message to a destination COEX entity.

FIG. 21D is a view showing semantics of a service primitive of a coexistence service change confirmation according to an embodiment of the present disclosure.

COEX_Servicechanging.confirm is used by the COEX entity in order to convey service changing information (servicechanging information) to the COEX user who has invoked the service changing request (Servicechanging request). A parameter of COEX_Servicechanging.confirm is defined as shown in Table 39 below.

TABLE 39 Name Data type Description SourceIdentifier COEX_ID It identifies an invoker of this primitive that may be a local COEX entity or a remote COEX entity. ResultCode Enumeration It reports the outcome of a request.

The parameter of COEX_Servicechanging.confirm is invoked by the local COEX entity in order to convey the results of COEX_Servicechanging.request primitive from a previous COEX user. When the COEX user receives this primitive, it makes an appropriate decision and takes suitable actions. However, when ResultsCode does not indicate “Success”, the recipient performs appropriate error handling.

FIG. 22 is a flow chart illustrating a process of switching a service by the CM 300 according to embodiments of the present invention.

First, the TVBD network or device 100 or the neighbor TVBD network or device 100′ is registered to the CM 300 and the CDIS/CDB 400. Also, the CM 300 and the neighbor CM 300′ are registered to the CDIS/CDB 400.

As mentioned above, the TVBD network or device 100 registered to the CM 300 and the CDIS/CDB 400 transmits a measurement report periodically or according to a request from the CM 300 (step S612). Also, as mentioned above, the neighbor CM 300′ and the neighbor TVBD network or device 100′ transmit a measurement report to the CDIS 400 according to a request from the neighbor CM 300′ (step S614).

The measurement report may include occupied channel information and interference level information of the TVBD network or device 100. The reason for the measurement report to include the interference level information of the TVBD network or device 100 is to accurately calculate a neighbor set in comparison to the case in which the existing CDIS/CDB 400 calculates a neighbor set by using only occupied channel information of the TVBD network or device 100.

When a resource allocation is requested, the TVBD network or device 100 may request resource allocation from the CM 300 (step S622). In this case, the TVBD network or device 100 may receive available channel information from the TVWS database 600 and transmit the same to the CM 300. When the request for a resource allocation is received from the TVBD network or device 100, the CM 300 requests a neighbor set from the CDIS/CDB 400 (step S624).

Here, the neighbor set may include information regarding a neighbor TVBD network or device 100′ of the TVBD network or device 100 and information regarding a neighbor CM 300′ serving the neighbor TVBD network or device 100′. The CDIS/CDB 400 may calculate a neighbor set on the basis of geographical location information (or geographical location information and the available channel information) of the TVBD networks or devices 100 registered to the CDIS/CDB 400 (step S626). The CM 300 may receive the calculated neighbor set from the CDIS/CDB 400 (step S628).

On the basis of the neighbor set, the CM 300 may request occupied channel information of the neighbor TVBD network or device 100′ from the neighbor CM 300′ (step S632). In this case, the CM 300 may transmit information regarding a neighbor TVBD network or device 100′ of the TVBD network or device 100 to the CM 300.

On the basis of the measurement report received from the neighbor TVBD network or device 100′, the neighbor CM 300′ may transmit occupied channel information of the neighbor TVBD network or device 100′ to the CM 300 (step S634).

On the basis of the available channel information of the TVBD network or device 100 and the occupied channel information of the neighbor TVBD network or device 100′ received from the neighbor CM 300′, the CM 300 may generate a priority table (step S636). The available channel information of the TVBD network or device 100 may be received by the TVBD network or device 100 from the TVWS database 600 and transferred to the CM 300, or the CM 300 may receive the available channel information of the TVBD network or device 100 from the TVWS database 600 or the CDIS/CDB 400 may receive the available channel information of the TVBD network or device 100 from the TVWS database 600 and transfer the same to the CM 300.

The CM 300 may transmit the generated priority table to TVBD network or device 100 (step S638). The reason for the CM 300 to receive the occupied channel information of the neighbor TVBD network or device 100′ from the neighbor CM 300′ is to determine a substantial available channel of the TVBD network or device 100.

On the basis of the priority table received from the CM 300, the TVBD network or device 100 determines whether to perform service switching (step S642). Namely, the TVBD network or device 100 checks whether or not there is a desired channel in the channels included in the available channels, and when there is no desired channel, in the available channels, the TVBD network or device 100 determines to switch a service.

In this case, the TVBD network or device 100 requests service switching from the CM 300 (step S644). The CM 300 switches a service in response to the request from the TVBD network or device 100 (step S646). In this case, the CM 300 may transmit a neighbor set to the TVBD network or device 100. In order to secure a desired channel, the TVBD network or device 100 may negotiate with the neighbor CM 300 about an available channel on the basis of the received neighbor set.

FIG. 23 is a schematic block diagram of the CM 300 according to the present disclosure.

As shown in FIG. 23, the CM 300 includes a storage unit 310, a controller 320, and a transceiver unit 330.

The storage unit 310 stores the method according to the embodiments illustrated in FIGS. 1 to 22.

The controller 320 controls the storage unit 310 and the transceiver unit 330. In detail, the controller 320 executes the foregoing methods stored in the storage unit 310. The controller 320 transmits the foregoing signals through the transceiver unit 330.

While the present invention has been shown and described in connection with the embodiments, it will be apparent to those skilled in the art that modifications and variations can be made without departing from the spirit and scope of the invention as defined by the appended claims. 

The invention claimed is:
 1. A method for changing service types, the method performed by an apparatus including a coexistence manager (CM) and comprising: receiving, by the apparatus from a server, information for a television band device (TVBD) network or device using a first service type in which an operating channel of the TVBD network or device is determined by the CM, wherein the information for the TVBD network or device includes neighbor information and interference information; wherein the neighbor information indicates an identification of a neighbor TVBD network or device, and wherein the interference information indicates an interference level with regards to the neighbor TVBD network or device, based on the information for the TVBD network or device, transmitting, by the apparatus to the TVBD network or device, a service type change request indicating a service type change from the first service type to a second service type in which the operating channel of the TVBD network or device is determined by the TVBD network or device; and receiving, by the apparatus from the TVBD network or device in response to the service type change request, a service type change response indicating whether the first service type has changed to the second service type, wherein the service type change request is a message for requesting a switchover from the first service type which is a management service in which the CM determines the operating channel of the TVBD network or device, to the second service type which is a discovery/information service in which the TVBD network or device determines the operating channel of the TVBD network or device.
 2. The method of claim 1, wherein the neighbor information is based on measurement results received from the TVBD network or device.
 3. The method of claim 1, wherein the CM receives the neighbor information from the server when the CM requires the neighbor information.
 4. The method of claim 3, wherein receiving the information for the TVBD network or device comprises: transmitting, by the CM to the server, a request for the neighbor information; and receiving, by the CM from the server, a response with respect to the request for the neighbor information.
 5. The method of claim 4, wherein the request for the neighbor information includes an identifier of the TVBD network or device.
 6. The method of claim 4, wherein the neighbor information includes an identifier of at least one neighbor CM serving the neighbor TVBD network or device.
 7. The method of claim 3, wherein receiving the information for the TVBD network or device comprises: receiving, by the CM, the neighbor information from the server without a request for the neighbor information.
 8. The method of claim 1, wherein the CM obtains the neighbor information from another CM.
 9. The method of claim 8, wherein the neighbor information includes information about operating channels of the neighbor TVBD network or device.
 10. The method of claim 1, wherein the TVBD network or device and the neighbor TVBD network or device use different types of network technologies.
 11. The method of claim 1, further comprising: selecting, by the CM, at least one channel which is not overlapped with a channel allocated to the neighbor TVBD network or device.
 12. The method of claim 1, wherein the neighbor information is based on operating channels of the TVBD network or device and the neighbor TVBD network or device.
 13. The method of claim 1, further comprising: negotiating with a neighbor CM serving the neighbor TVBD network or device, regarding frequency bands.
 14. An apparatus including a coexistence manager (CM), the apparatus comprising: a transceiver unit; and a controller configured to control the transceiver unit to receive, from a server, information for a television band device (TVBD) network or device using a first service type in which an operating channel of the TVBD network or device is determined by the CM, wherein the information for the TVBD network or device includes neighbor information and interference information, based on the information of the TVBD network of device, transmit, to the TVBD network or device, a service type change request indicating a service type change from the first service type to a second service type in which the operating channel of the TVBD network or device is determined by the TVBD network or device, and receive, from the TVBD network or device in response to the service type change request, a service type change response indicating whether the first service type has changed to the second service type, wherein the neighbor information indicates an identification of a neighbor TVBD network or device, wherein the interference information indicates an interference level with regards to the neighbor TVBD network or device, and wherein the service type change request is a message for requesting a switchover from the first service type which is a management service in which the CM determines the operating channel of the TVBD network or device, to the second service type which is a discovery/information service in which the TVBD network or device determines the operating channel of the TVBD network or device.
 15. The apparatus of claim 14, wherein the neighbor information is based on measurement results received from the TVBD network or device.
 16. The apparatus of claim 14, wherein the controller is configured to control the transceiver unit to receive the neighbor information from a server when the CM requires the neighbor information.
 17. The apparatus of claim 14, wherein the controller is configured to control the transceiver unit to receive the neighbor information from another CM.
 18. The apparatus of claim 14, wherein the controller is configured to select at least one channel which is not overlapped with a channel allocated to the neighbor TVBD network or device.
 19. The apparatus of claim 14, wherein the neighbor information is based on operating channels of the TVBD network or device and the neighbor TVBD network or device.
 20. The apparatus of claim 14, wherein the controller is configured to negotiate with a neighbor CM serving the neighbor TVBD network or device, regarding frequency bands. 